Remove refresh_token from cookie instead of setting to NULL#193
Merged
Conversation
44a4e56 to
31647ff
Compare
nandan-bhat
approved these changes
Nov 24, 2025
31647ff to
a210c7d
Compare
Merged
This was referenced Dec 5, 2025
6 tasks
This was referenced Jun 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR improves the handling of refresh token failures in the Auth0 ASP.NET Core Authentication library.
Fix
OnMissingRefreshTokenevent is triggered on subsequent requests.OnMissingRefreshTokenis called after a refresh token failure and subsequent request.References
Testing
Should_Call_OnMissingRefreshToken_After_Refresh_Failstest added to simluate simulate a scenarios where refresh fails.This change adds test coverage for new/changed/fixed functionality
Checklist
mainNote : This fix is based on the issue raised by janruo in #191 . The fix will be attributed to @janruo during release.